Backported the split parfor pass from upstream Numba. #949
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Splits the parfor pass into separate Parfor, ParforFusion
and ParforPreLowering passes.
- Introduces a "lowerer" attribute into parfor nodes to help
use different lowerers based on compute follows data
programming model.
|
Merging based on public CI. The coverage drop needs proper addressing. |
github-actions bot
added a commit
that referenced
this pull request
Mar 3, 2023
…sses Backported the split parfor pass from upstream Numba. 1c1f371
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Have you provided a meaningful PR description?
Back ports the new Parfor pass from Split parfor pass into 3 parts. (old) numba/numba#8725
and ParforPreLowering passes.
use different lowerers based on compute follows data
programming model.
Have you added a test, reproducer or referred to an issue with a reproducer?
Have you tested your changes locally for CPU and GPU devices?
Have you made sure that new changes do not introduce compiler warnings?
If this PR is a work in progress, are you filing the PR as a draft?